System for Balancing Dampening Forces on a Suspension System

ABSTRACT

A system for adjusting the damper force on the suspension system of a bicycle is provided. Sensors are placed on the front shock and rear shock to measure the amplitude of displacement or acceleration in the time domain and generate a zenith position, velocity, force, and work based on the measured values. The system calculates a curve fit approximation curve for the relationships of zenith position versus velocity and uses the approximation curves to generate and display recommended damper settings for the front shock and rear shock. Using the data ensures that the bicycle suspension data is balanced, such that the front shock and rear shock respond similarly to the same event.

BACKGROUND OF THE INVENTION

The present invention relates generally to the field of telemetry datafor multi-wheel suspension. The present invention relates specificallyto a system to balance a suspension system based on actual suspensionperformance data. Multi-wheel suspension systems have at least twodifferent adjustable dampers and may have up to 200,000 differentcombinations of settings for each damper. It is desired to use actualdata to fine-tune those settings in order to enhance the overallperformance of the bike suspension system.

SUMMARY OF THE INVENTION

One embodiment of the invention relates to a system for adjusting adamping force on the suspension of a bicycle. The system includes alinear position sensor coupled to a front shock of a bicycle to generatea vertical fork deflection signal representative of the verticaldeflection of the front shock. The system includes another sensorcoupled to a rear shock of a bicycle to precisely measure the positionof the rear shock. A processor is coupled to the sensors. The processorgenerates front shock and rear shock velocity data representative of avertical component of velocity of the front shock and rear shock basedupon the signals. The processor generates front shock and rear shockacceleration data representative of the vertical acceleration of thefront shock and rear shock based upon the signals. The processorgenerates zenith position data for the front shock and rear shockrepresentative of a vertical zenith position based on the front shockand rear shock acceleration data, and generates an approximation curvevideo signal based upon the velocity data and zenith position data forthe front shock and rear shock. A display is coupled to the processorand configured to generate a visual representation of the velocity tozenith position based upon the approximation curve video signal computedfor the front shock and the rear shock. The visual representationincludes a curve fit analysis of the velocity data versus zenithposition data for the front shock and the rear shock. Adjustments to thedamping force of the front shock and rear shock are based upon the curvefit analysis.

Another embodiment of the invention relates to a system for adjusting adamping force on a suspension of a bicycle. The system includes a frontshock sensor coupled to a front shock of a bicycle to generate avertical fork acceleration signal representative of the verticalacceleration of the front shock. A rear shock sensor is coupled to arear shock of a bicycle to generate a vertical rear acceleration signalrepresentative of the vertical acceleration of the rear shock. Aprocessor is coupled to the sensors. The processor generates front shockand rear shock velocity data representative of a vertical component ofvelocity of the front shock and rear shock based upon the signals. Theprocessor can generate zenith position data for the front shock and rearshock based on the acceleration signal representative of the verticalacceleration of the front shock and rear shock, and generates anapproximation curve video signal based upon the velocity and zenithposition data. A display is coupled to the processor and configured tosimultaneously generate a visual representation of the velocity tozenith position based upon the approximation curve video signalscomputed for the front shock and rear shock. The visual representationincludes a curve fit analysis of the vertical component of velocityversus zenith position of the front shock and the rear shock. Thedisplay recommends adjustments to the damping force at the front shockand rear shock based upon the curve fit analysis.

Another embodiment of the invention relates to a device for displayingparameters of a suspension system for a bicycle. Electronic memorystores user inputs and result data for a front shock and a rear shock. Asetup module obtains information related to the front shock and the rearshock on a suspension system of the bicycle. The setup module includes afront shock module and a rear shock module. The front shock moduleobtains a calibrated vertical displacement of the front shock and storesa head tube angle of the front shock. The rear shock module obtains acalibrated vertical displacement of the rear shock and stores a rearshock angle of the rear shock. A record module records events during aride. The record module obtains the vertical displacement, velocity, andacceleration of the front shock and rear shock for each event and storesthe vertical displacement, velocity, and acceleration of the front shockand the rear shock in electronic memory. A results module accesses theresults of the record module and setup module to calculate the verticalforce and vertical work components for each event at the front shock andrear shock. The results module generates a curve fit analysis of thevertical zenith position component versus velocity for the front shockand rear shock. The results module compares the curve fit analysis forthe zenith position and velocity components at the front shock with thecurve fit analysis for the zenith position and velocity components atthe rear shock. Adjustments for the front shock and the rear shock arebased on the comparison of the curve fit analysis for zenith positionand velocity components of the front shock and the rear shock.

Alternative exemplary embodiments relate to other features andcombinations of features as may be generally recited in the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

This system will become more fully understood from the followingdetailed description, taken in conjunction with the accompanyingfigures, wherein like reference numerals refer to like elements inwhich:

FIG. 1 illustrates a system for measuring the deflection, velocity, andacceleration of a multi-wheeled suspension system to calibrate thesuspension system, according to an exemplary embodiment.

FIG. 2 is a detailed view of the front shock or fork on the suspensionsystem illustrated in FIG. 1, according to an exemplary embodiment.

FIG. 3 is a detailed view of a rear shock or shock on a suspensionsystem illustrated in FIG. 1, according to an exemplary embodiment.

FIG. 4 is an image of a record module to record the events withcalibrated and installed sensors, according to an exemplary embodiment.

FIG. 5 is a bike setup module, where the model and geometry of the frontshock and rear shock are identified, the leverage ratio is identified tocalculate the rear axle vertical position relative to the instantaneousshock position, according to an exemplary embodiment.

FIG. 6 illustrates a vector normalization of the obtained displacementsto measure the vertical component of the fork, according to an exemplaryembodiment.

FIG. 7 is a user interface where user notes are input into the system,and details about the performance are annotated, according to anexemplary embodiment.

FIG. 8 is a summary page of the results module providing summary data ofthe ride and events, according to an exemplary embodiment.

FIG. 9 is a continuation of the summary page of the results moduleillustrated in FIG. 8, according to an exemplary embodiment.

FIG. 10 illustrates a histogram of the derived compression speeds andrebound speeds for a ride, according to an exemplary embodiment.

FIG. 11 is a waveform of a ride with multiple events.

FIG. 12 is the waveform of FIG. 11 zoomed in to show the waveform of theevents.

FIG. 13 is a regression analysis of a speed of compression and a damperrebound.

FIG. 14 is a GPS tracker for a ride, illustrating the locations ofevents and where the ride began and ended, according to an exemplaryembodiment.

DETAILED DESCRIPTION

Referring generally to the figures, various embodiments of a system 10to adjust a dampening force on a suspension system of a bicycle areshown. Many of today's bicycles use shock absorption to improve theriding experience, enhance traction on slopes or slippery terrain,and/or reduce the force distributed to the rider's wrists or body.Sensors on the shock absorbers measure the deflection of the shockabsorbers. With this data, system 10 can determine the zenith position,velocity of the deflection, the acceleration, and the forces distributedto the front shock (or “fork”) and rear shock (or “shock”). The speed ofcompression or rebound, as well as the absolute force/work of thedeflection and rebound, are important balance metrics that determine howthe suspension system is performing. Sensors may capture and collect rawdeflection and/or acceleration data and communicate the data throughtelemetry to a smartphone or other device.

Obtaining shock absorption raw deflection data for a post-ride analysisis the first step to understand how a suspension system behaves.However, raw deflection data represents a multitude of events for asingle ride. The deflection data represents a collection ofinstantaneous position samples for each deflection event in the timedomain. Instantaneous position samples may be made along with anine-axis accelerometer, gyro, and direction sensor based on the earth'smagnetic field. The instantaneous position of a fork damper and shockabsorber damper are sampled at a specified frequency. A method ofturning this raw data into analytical results for improving the ridingexperience is sought that enables setting the parameters of the shockabsorber according to the results of objective deflection data. Byvisualizing the results, a rider will “see” how the suspension systemperforms during actual events measured during a ride and how to adjustthe suspension system to enhance performance.

Each damper on a bicycle should deflect a similar amount for each event.In addition, the speed of the deflection is also relevant. If the frontand rear shocks both deflect equal distances but at different times, therider experiences an imbalance. The ultimate goal in tuning dampedsuspension systems is to ensure that each damper behaves similarly. Formotorcycles, bicycles, or other multi-wheeled vehicles, the balancebetween the front shock absorber and the rear shock absorber requiresunderstanding the system as a whole, not just individual dampers. Thisrequires comparing the shock absorber performance.

Typical dampers are adjustable to enable a rider to configure damperresponse to a force (e.g., an event). Some of the adjustments includecompression, rebound, spring rate, spring progressivity, and othersettings that an operator “tunes” on each damper. For example,compression and rebound adjustments typically include two differentdamper tuners for high and low-speed events. In all, a single damper canhave 200,000 or more unique combinations. To understand the system as awhole, both the front and rear damper must be analyzed together. Whenpaired with another damper, the combinations of settings can becomeunwieldy. Applicant has found that by taking the data of a ride andvisualizing the results, an operator can tune the settings to achievegreater suspension balance.

A control process is sought so that an operator can tune the dampers asa system and achieve an enhanced riding experience based on the results.To better understand the dynamic forces of an event with multipledampers, a system is sought to systematically inform the user onpreferred settings based on actual riding events. Based on this controlsystem, the operator should quickly “see” whether the system is balancedand make adjustments accordingly. Visualization of the data furtherensures that each damper responds as part of a complete system accordingto unique bicycle characteristics and/or rider preferences. Applicanthas found that by separating the data from the sensors into compressiondata and rebound data, and optionally further classifying the data byevent type, the regression lines of the processed data provide a systemto visualize suspension balance and make adjustments.

A data or curve fit such as a regression analysis can simplify acomprehensive scatter-plot of all events for analysis of particular datasamples indicative of the vehicle's dynamic response. For example, adisplacement versus velocity plot of each event creates a largescatter-plot of the front and rear shock performance. A regressionanalysis line enhances understanding through visual simplification ofthe results. Using a filter to organize scatter-plot data intocollections of discrete events (e.g., left-hand turns, jumps, orvertical climbs, or rocky descents). This enables the system to analyzeperformance for each classification and ensure appropriate shockabsorption settings for each event type.

The processor separates the data obtained from the time domain intocompression events and rebound events. The processor can then perform aregression analysis for either the complete scatter-plot or a limitedscatter-plot limited for a collection of discrete events. To visualizethe damper balance, the processor classifies the events as a compressionor rebound in the time domain. The real-time graph records compressionsas upward movements and rebounds as downward movements. This data isconverted to a scatter-plot for compression events and a scatter-plotfor rebound events. The scatter-plot generates a velocity of thecontraction or rebound along the y-axis, versus a total displacement onthe x-axis for each event. Once the system plots the regression linesfor the front shock and the rear shock, the user or system can comparethe lines. The bike is tuned or balanced when the regression linesrepresenting the rebound or compression of the front and rear shocks areparallel. In practice, perfectly parallel lines are seldom achieved, butthe process gives a mechanism to visualize the performance of thesuspension system and make improvements to the system based on data.

FIG. 1 illustrates a control system 10 for adjusting a dampening forceon a suspension system 11. A front shock damper, or fork 12, and a rearshock damper, or shock 14, are illustrated. The fork 12 has forkadjustments 16 that increase or decrease the spring constant, dampingforce, and other parameters of the front suspension. A Tracer™(Trademark Serial No. 87,556,462 owned by Motion Instruments Inc.) orsensor 18 measures the deflection of the fork 12 through time. A frontshock sensor or fork sensor 18 can couple to a fork 12 of a bicyclesuspension system 11 to generate a vertical fork 12 deflection signal.The deflection signal represents the vertical deflection or displacementof the front shock or fork 12.

Similarly, shock 14 has shock adjustments 20 that increase or decreasethe spring constant, damping force, or other parameters of the rearsuspension. A tracer or sensor 22 measures the deflection of the shock14 through time. The rear shock sensor 22 couples to a rear shock 14 ofthe bicycle suspension system 11 in conjunction with a leverage curve tocalculate rear axle position derived from shock position to generate avertical rear deflection signal representative of the verticaldeflection of the rear shock 14.

The balance of the suspension system 11 includes the combined effects ofthe fork 12 and shock 14. Sensors 18 and 22 measure the magnitude of thedeflections of the fork 12 and shock 16 as an operator rides thebicycle. When the ride is completed, a processor 24 (e.g., a desktopcomputer, a laptop, a tablet such as an iPad or Android device, asmart-phone such as an iPhone or Android, or another electronic device)connects to the front and rear sensors 18 and 22 to measure thedeflection of the suspension system 11. The processor 24 connection mayuse wires, as shown in FIG. 1, or may connect wirelessly via Bluetooth,Wi-Fi, or other wireless connections.

When the tablet or processor 24 connects to sensors 18 and 22 itprocesses (e.g., downloads, stores, and analyzes) the deflection datameasured over the course of the ride. The processor 24 can process thedata and calculate a velocity of the deflections based on the magnitudesin the time domain. The system 10 also computes an acceleration of thedeflections per unit time (e.g., by taking the anti-derivatives of themeasured deflections in the time domain). System 10 is calibrated withthe mass of the rider to determine the sag. System 10 can obtain orcompute the acceleration. Thus, the processor can also determine theforce generated by each event. Using the processes described below,processor 24 can assemble the data into a visual display of suspensionsystem 11. This visualized data can help calibration and tuning of thefork 12 and shock 14 of the suspension system 11.

Processor 24 may couple to the sensors 18 and 22. Processor 24 mayobtain raw deflection displacement and/or acceleration data from thesensors 18 and 22 connected to the fork 12 or shock 14 during an event.An event may include a right or left-hand turn, a jump, a climb, a bump,a drop, or another event that utilizes the damping force of thesuspension system 11. For example, sensors 18 and 22 are positionsensors that can capture raw deflection displacement data for an event.Processor 24 may obtain raw acceleration data from sensors 18 and 22connected to the fork 12 or shock 14. For example, the accelerationsensors 18 and 22 are accelerometers that capture raw acceleration datafor an event. Processor 24 may use the obtained raw deflection(displacement or acceleration) data to compute vertical components ofthe deflection in the vertical direction. For example, the processor mayuse a head fork angle and rear shock geometry to convert the raw datainto vertical components of deflection.

Based on the vertical components of the displacement or acceleration,processor 24 can generate fork 12 or shock 14 velocity data. Thevelocity data is representative of a vertical component of the velocityof the front shock or fork 12 and rear shock 14 based upon the rawdisplacement or acceleration signals received by sensors 18 and 22. Forexample, the rear axle deflection is derived from the shock data usingthe leverage ratio of the bike. System 10 compares the axle deflectionsof the front wheel and rear wheel in the vertical direction. A system 10that obtains raw displacement data can generate fork 12 and rear shock14 acceleration data by deriving the vertical component of velocity. Theprocessor 24 can anti-derive the vertical component of raw accelerationdata at the fork 12 or rear shock 14 based upon the vertical componentof the acceleration signals to generate a vertical velocity. Thus,processor 24 may obtain raw displacement data or raw acceleration dataand generate vertical components of displacement, velocity, andacceleration in the fork 12 and rear shock 14.

Processor 24 may use a similar process to generate force data in thevertical direction for the fork 12 and rear shock 14. For example, theforce is equal to the mass times the acceleration. Control system 10 iscalibrated with a mass (e.g., sag) and processor 24 may obtain orgenerate a vertical acceleration to compute a force for each event. Inthis way, the raw displacement data and/or raw acceleration data cangenerate a vertical force based on the fork 12 or rear shock 14 verticalacceleration data for each event.

Similarly, processor 24 can generate total work for each event. Work isa function of force and displacement and processor can generate avertical component of force and displacement in the fork 12 and rearshock 14. Thus, vertical components of displacement, zenith positiondata, velocity, acceleration, force, and work are obtained from a singledisplacement or acceleration obtained by sensors 18 and/or 22. Moreover,the obtained components for the fork 12 and shock 14 are independent foreach event, such that the fork 12 and shock 14 may have differentcomponents of displacement, zenith position data, velocity,acceleration, force, or work for the same event.

Processor 24 can generate approximation curves, such as regressionlines, curves, exponential curve fits, or other best-fit continuousfunctions, from the obtained components at the fork 12 and shock 14.Based on the approximation curves, processor 24 generates a video signalbased upon the velocity data and zenith position data for the fork 12and rear shock 14. In some embodiments, the approximation curve is basedon the zenith position data of the front axle at the fork 12 and therear axle derived by the deflection rear shock 14 data. For example,processor 24 may compare the zenith position and velocity data for thefork 12 to the shock 14 and make recommendations to damper forceadjustments based on the approximation curves. For example, system 10may make recommendations based on the slopes of the regression lines forthe fork 12 and shock 14.

The fork 12 and shock 14 are calibrated with a sag displacement based onthe rider's weight on a stationary bicycle. An event occurs when thedisplacement on the fork 12 and/or shock 14 are compressed or reboundingabove a threshold value from the calibrated sag displacement. In otherwords, an event includes all displacements beyond a threshold value ofthe sag. Zenith position data filters the event data to obtain a maximumdisplacement in the vertical direction for the wheel axle at the fork 12or shock 14 during an event. The zenith position represents the maximumdisplacement of the fork 12 or shock 14 in the vertical direction and iscompared to the maximum velocity in the vertical direction to create azenith position versus velocity approximation curve.

Processor 24 can compute the velocity versus zenith position data forrecorded events and generate a fork 12 and a shock 14 regression linefor the front axle and rear axle (e.g., derived from the signals at thefork sensor 18 and rear shock sensor 22). The regression line may be thezenith position versus velocity and/or the work for the deflection andrebound data versus velocity. The slope of the fork 12 regression lineis compared to the slope of the rear shock 14 regression line toestablish the recommended adjustments of the front shock and the rearshock. The recommendations may make the slopes of the regression linesparallel or nearly parallel (e.g., within 15 degrees of parallel). Insome embodiments, the slope of the regression lines are adjusted towithin 5°, 10°, 15°, 20°, 25°, or 30° of parallel. In some embodiments,the curve fit of an approximation curve for the fork 12 is compared toan approximation curve for the shock 14 and adjusted to generate thesame curved shape and/or minimize the distance between the curves.

A display can couple to the processor to generate a visualrepresentation of the velocity to zenith position approximation curvevideo signal. The processor 24 computes the signal for the fork 12 andrear shock 14. The visual representation can include curve fit analysisof the velocity data versus zenith position data for the fork 12 andrear shock 14, in a variety of formats. For example, the visualrepresentation may include a scatter point plot with the raw dataillustrated or may include only a curve fit of the raw data. The curvefit may include any continuous function that represents a continuousapproximation of the zenith position data, velocity data, and/or workdata. The display can further recommend adjustments to the damping forceat the fork 12 and/or rear shock 14 based upon analysis of the curvefit.

Display 26 may be an application on a smartphone or tablet. Display 26may be a computer or printer. Display 26 may illustrate recordedwaveforms of the vertical displacement or acceleration signals thatgenerate the zenith position, velocity, force, and work data for thefork 12 and rear shock 14 in the time domain.

FIG. 2 illustrates a detailed view of a fork 12 showing the location ofthe fork adjustments 16 and fork sensors 18. Similarly, FIG. 3illustrates a detailed view of a shock 14 illustrated the placement ofshock adjustments 20 and shock sensors 22. The component hardwareillustrated in FIGS. 1-3 will be referred to throughout the applicationwith the assigned reference numbers previously described. A complexsuspension system 11 (e.g., with 200,000 settings for each shockabsorber) can have billions of adjustable combinations. Control system10 enhances suspension system 11 performance through an adjustmentprocess.

FIG. 4 illustrates a home-screen 100 of control system 10. At startup,the home-screen 100 is displayed. From the home-screen 100, the operatorcan access most of the features of the system 10 and can see a summaryof pertinent results. The home-screen 100 allows the operator tointeract with the system 10 and record riding events and data. Thehome-screen 100 includes hyperlinks and/or displays for a bike setupmodule 102, a battery indicator 104, a relative/absolute measurementtoggle 106, a maximum display 108, a sag indicator 110, and a notemodule 112. Home-screen 100 further includes a toggle bar 111 thatincludes an off toggle 114, a live toggle 116, a record toggle 118, andan auto toggle 120. Home-screen 100 can also hyperlink to a GPS module122. Four components of control system 10 include a record module 124,results module 126, report module 128, and an about/help module 130.

When the operator first loads the home-screen 100 and presses the bikesetup hyperlink 102 on the home-screen 100, system 10 loads the bikesetup module 200 illustrated in FIG. 5. Bike setup module 200 enablesthe operator to input information to record data from one or moresensors on the suspension system. Bike setup module 200 enables theoperator to input information about the bike, the suspension system, thesensors, and other pertinent parameters to begin recording a ride. Amodel input 202 allows the operator to input a standard bike model intothe system 10. In some embodiments, model input 202 displays a list ofavailable models. In some embodiments, model input 202 searches an inputmodel name or number to determine the correct bike model. Model input202 may ask the user to confirm the selected or identified bike model.

Name 204 enables a user to name the bike and/or give a customized nameto the results obtained on a bike. The name 204 may allow one bike to bestored at a time or several bikes can be stored in the system withdifferent customized names 204.

The rear axle ratio is a measurement of the amount of travel at the rearwheel relative to the displacement at the shock 14. It is a ratio, so arear axle ratio of one means that the distance the shock 14 travels isequal to the distance the rear wheel travels. The rear axle ratio isdetermined by the system 10 based on the model input 202 of the bike. Insome embodiments, the rear axle ratio is determined by system 10 basedon the user input shock model 220. If system 10 does not support thebike model input 202, the user can customize the rear axle ratio (e.g.,by inputting the shock model 220 number). The system 10 may preventusers from editing the rear axle ratio or may allow different versionsof system 10 to access or adjust this ratio.

The connect button 208 pairs system 10 with the sensors 18 and 22. Thesystem 10 can be paired through bluetooth, WiFi, a network connection,through electric cables or wires (as illustrated in FIG. 1), or by otherelectronic means. The connect button 208 can determine whether sensors18 and 22 at the front fork 12 and rear shock 14 are actively outputtingdata and whether system 10 can record the data.

The fork model 210 and shock model 220 allow a user to input modelnumbers or otherwise identify the shocks on the bike. For example, acustomized bike may have different fork 12 and shock 14 models 210 and220 than indicated based on the model input 202 number. Identifying thefork model 210 and shock model 220 defines the maximum fork travel 212and maximum shock travel 222 respectively. In some embodiments, theoperator cannot edit the maximum fork travel 212 or maximum shock travel222 data. System 10 may select the data based on the input fork/shockmodel numbers 210 and 220. In other embodiments, the application allowsthe user to input the maximum fork travel 212 and maximum shock travel222 without defining the fork model 210 or shock model 220.

The fork tracer ID 214 and shock tracer ID 224 identify the sensors 18and 22 at the fork 12 and shock 14, respectively. The fork tracer length216 and shock tracer length 226 are selected so that the sensors candetect a distance greater than or equal to the maximum fork travel 212or maximum shock travel 222.

The fork tracer calibration 218 and shock tracer calibration 228 outputthe results obtained from calibration module 230. Calibration module 230and fork/shock tracer calibration numbers are not user programmable. Tocalibrate the sensors, the operator lifts the bike off the ground tocompletely unload the suspension system 11. When the calibration module230 is activated (e.g., the “Calibrate All Tracers” hyperlink isselected), the bottom of the shock absorber (e.g., the fork 12 and rearshock 14) is defined. This process sets the “zero” value of the sensor18 and 22 on the suspension system (e.g., the minimum deflection).Because the sensor 18 and 22 length is longer than the maximum travel(e.g., stroke length) of the suspension, the system 10 must calibratethe minimum deflection, or bottom, of the suspension system 11. Oncecalibrated, all displacements are determined relative to the set zerovalue. Once the user enters the calibration module 230, the user cannotexit the module 230 without tapping the “Calibrate All Tracers”hyperlink. If the user tries to exit, system 10 generates a warning andthe data obtained may not provide accurate results.

Once the bike is set-up, the user can either select reset 232 to removeall values and start over or press done 234 to save the data and returnto the home-screen 100. The reset 232 button may enable the correctionof mistakes or to adjust system 10 for use with another bike. When done234 is selected the data in the bike setup module 200 is stored for thesuspension system 11 and the user returns to the home-screen 100.

Returning to FIG. 4, the home-screen 100 includes a battery indicator104. Battery indicator 104 appears when the tracers or sensors 18 and 22connect to system 10. System 10 reads the battery strength of thesensors 18 and 22 and adjusts the displayed battery levels according tothe reading. When the battery level appears, it means the system 10 isconnected to the sensor and ready to record. If the system 10 cannotconnect to the battery, a spinning wheel in the same place the batterywould appear indicates the system 10 cannot connect to the sensors 18and 22. The sensor 18 or 22 may include an accelerometer that requiresan adequate power supply to operate. Thus, battery indicator 104 mayindicate when batteries should be replaced for a long ride or when powerto an accelerometer is absent or generates inaccurate results. System 10may implement a power saving measure on the sensor to put the unit tosleep when sensor 18 or 22 is not connected or after a period of non-use(e.g., after 5 minutes). The battery indicator 104 visually indicateswhether the sensors are transmitting data or connecting to the system10. In the event the sensor 18 and 22 has adequate power but is in sleepmode, the operator can shake the bike and activate sensors 18 and 22.Once sensors 18 and 22 are advertising to system 10, battery indicator104 shows the power supply available.

System 10 uses sensors to detect deflections in the vertical directions.The distances of these deflections are used to determine the velocityand acceleration as anti-derivatives of the position. The measureddeflections are not generally in the vertical direction. For example,with reference to FIG. 6 illustrating a vertical speed normalization,the forks movement 302 (and velocity) is the sum of two componentvectors (e.g., a horizontal component 304 and a vertical component 306).The component vectors can be obtained based on the head tube angle 308of the fork 12. In this way, processor 24 can obtain a horizontalcomponent 304 and a vertical component of the fork position, speed, andacceleration. Since the objective of the suspension system is to matchthe vertical displacement at the fork 12 to the vertical displacement ofthe shock 14 for the suspension system 11, the horizontal component 304may be removed and the vertical component 306 of fork 12 compared to thevertical component of shock 14. The geometry of the shock 14 issimilarly used to determine vertical components of the position, speed,and acceleration that can be matched or compared to the verticalcomponents 306 of the fork 12.

Similarly, the deflection of the rear shock 14 is determined in thevertical direction. The shock position is measured and the rear axlevertical displacement is calculated using the leverage curve of thebicycle. The leverage curve is a value on a table based on the model ofthe shock 14. The displacement in the shock 14 is related to adisplacement of the axle of the rear wheel. For example, a position of100 mm on shock 14 corresponds to vertical position 86 mm on the rearaxle. In some embodiments, the rear axle vertical displacement iscalculated using the leverage curve of the bicycle. In otherembodiments, the manufacturer provides a rear axle position. A pivotsensor can measure the angle of the pivot. The pivot sensor can measurethe relative angle between two pivot points with an angle sensor. Thepivot sensor measures the deflection based on measured deflections oftwo angles on a pivot.

FIG. 4 illustrates a relative/absolute measurement toggle 106 thatallows a user to determine whether these vertical components 306 areconveyed to the user in absolute or relative terms. For example, system10 may display an absolute deflection of 35 mm to indicate an event.Similarly, system 10 may display a 17.5% deflection to indicate the sameevent (e.g., a 35 mm deflection divided by a 200 mm max deflection).Depending on the desired result, a relative or absolute measurement maybe preferred, and toggle 106 enables user selection of the displayedresult.

Home-screen 100 may include a maximum displacement display 108,indicating the furthest sensor displacement (e.g., from calibrated“zero”) obtained since the system 10 was turned on or for a downloadedset of data points. This number can be displayed as an absolute value(e.g., mm) or as a relative value (percent of total displacement).

Similarly, home-screen 100 can display the amount of sag 110 in absoluteor relative terms. Static sag 110 measures the deflection caused by astationary rider sitting on the bike. Sag 110 defines the preload in thedamper caused by the rider's weight. Suspension manufacturers providerecommendations for the preload on the fork 12 and shock 14 absorbersbased on the damper spring rate. In some embodiments, the spring ratecan be adjusted by adding or removing air pressure from the damper,allowing for more or less preload and/or rider weight.

Selecting the note module 112 hyperlink on home-screen 100 loads a notemodule 400, illustrated in FIG. 7 that allows the user to capture thefork 12 settings and shock 14 settings on a particular ride. This may beuseful if adjustments are made to the settings to be able to “revertback” or compare old and new results. Note module 400 may include alocation or trail name 402 as well as a trail condition 404 input. Theuser may identify keywords 406 to identify a particular ride or eventclassification. The rider may input any general notes 408 using speechrecognition and rate the ride results with a score 410. Fork parameters412 may also be recorded for a particular ride. Fork parameters 412 mayinclude the tire pressure, spacers, preload pressure, compressiondamping (high), compression damping (low), rebound damping (high),rebound damping (low), preload spring rate, preload spring setting, andother parameters. The same or similar shock parameters 414 can beannotated and recorded for the rear shock. The user can return to thehome-screen 100 by pressing the cancel button 416 or the done button418. The cancel button 416 returns to the home-screen 100 without savingthe changes, whereas the done button 418 returns to the home-screen 100after saving the annotations.

Returning to FIG. 4, a toggle bar 111 may allow selection of fourdifferent recording modes. Off toggle 114 means that the sensors arepowered off, and system 10 is not recording any displacement data. Thelive toggle 116 displays displacements of the sensors in real-time onthe real-time display 132, but may not record the results in long-termmemory. The user may view the instantaneous displacements, but system 10won't save the results for future analysis. The record toggle 118records all displacements upon pressing the button. The real-timeresults are displayed on the real-time display 132 and stored for futureretrieval and/or analysis. System 10 records every displacement orabsence of displacement at a fixed frequency (e.g., 200 Hz) in recordmode 118. Different sample frequencies may be used and can depend uponthe bandwidth of system 10 to the connection of sensors 18 and 22. Forexample, the frequency can be 100, 120, 140, 160, 180, 200, 220, 240,260, 280, 300, 320, 340, 360, 380, or 400 Hz, based upon the bandwidthof the connection to sensors 18 and 22. The auto toggle button 120 issimilar to the record toggle 118 except that system 10 automaticallydiscards “junk data” (e.g., data obtained in the absence of adisplacement or when a sensor is not operating correctly). Auto toggle120 only records data when the bike is moving (e.g., it stops recordingwhen the rider stops to take a break) and trims the file size of theresults by removing stationary data. When the operator is done recordingin either record mode 118 or auto mode 120 system 10 presents the userwith an option to store or discard the data.

As described in further detail below, the home-screen 100 may include aGPS module 122 hyperlink to record the GPS coordinates of a ride. Thehome-screen 100 also includes selection buttons for four primarysections of control system 10. The record module 124 receives input datafor recording a ride and is accessed through the default home-screen100, as described above. The record module 124 allows the user to definethe bike, connect the sensors, and record data. For example, recordmodule 124 records data at a fixed frequency. Record module 124 couplesto display 26 to generate waveforms of the vertical component of thedisplacement, velocity, and acceleration in a time domain. The resultsmodule 126 lets the user navigate to different graphics and tables tovisualize the data. The report module 128 generates a standardizedreport that compares several previously recorded rides. This page allowsthe user to compare bike settings and recorded metrics side-by-side andallows comparison testing between alternative fork 12 and shock 14settings. The about/help module 130 provides system 10 firmware andfirmware versions of sensors 18 and 22. The module may contain marketinginformation, search functionality, help pages, and/or instructions forconnecting sensors 18 and 22 to a bicycle.

FIGS. 8-13 illustrate the results module 126 in further detail. Oncedata is acquired, the user can press the results module 126 onhome-screen 100 to open the summary results module 500 illustrated inFIG. 8. The results module 500 has three main components: the frontsuspension component 502, the rear suspension component 504, and thebalance component 506. The front suspension component 502 isolates thesummarized results to the front suspension or fork 12. Similarly, therear suspension component 504 displays summarized results for the rearsuspension or shock 14. Front suspension component 502 data is displayedin FIG. 8 for fork 12. The same or similar data is available for therear shock 14 in rear suspension component 504. The balance component506 analyzes the suspension system 11 as a whole and includes data fromthe front fork 12 and the rear shock 14.

The current file 508 displays the loaded file for analysis (e.g., FIG. 8displays the file “robertsiPhone-08-12-05”). Current file 508 is ahyperlink and can be altered or replaced by tapping on the hyperlink.When activated the hyperlink provides a list of previously recordedfiles displaying the files currently stored in system 10. Files can bestored locally or on a network. In some embodiments, the current files508 include only files saved on a local drive. In other embodiments, thecurrent files 508 include files on a local drive and/or a network (e.g.,cloud drive). A download file button 510 allows the user to download afile stored on a network to a local drive.

The recorded waveform module 512 allows for visual inspection of rawdata. The waveform (e.g., illustrated in FIGS. 11 and 12) shows the rawsensor data displayed in the time domain. The recorded waveform module512 allows users to drill into specific events of a ride and to see theactual waveform generated by the sensors. In some embodiments, differentfilters 516 display or remove specific data. For example, a user canremove a checkbox from system 10 to remove the data for a particularfilter from the screen. The recorded waveforms 512 are described ingreater detail below with reference to FIGS. 11 and 12.

The results screen may have a similar GPS hyperlink 514 as hyperlink 122displayed on the home-screen 100 of record module 124. GPS hyperlinks122 and 514 may display the GPS module 900 shown in FIG. 14 described inreference to that figure below.

A filter 516 may screen out data or events that the user doesn't wantanalyzed. For example, using filter 516, a user can analyze the fork 12and shock 14 data for all right turn events during a ride recorded on afile 508. Filter 516 may also filter compression and rebound strokesthat don't meet a minimum or maximum amplitude or time constraint. Noteshyperlink 518 may connect the user to the note module 400 describedabove. A mail icon 520 may allow the user to email the data to himselfor customer support for help analyzing a file 508. An upload hyperlink522 allows the user to zip the recorded file 508 and transfer the file508 via text messaging, AirDrop, to a network through WiFi or cellcoverage, using an application such as MotionIQ™ (Trademark Serial No.87,556,457 owned by Motion Instruments Inc.), or other software with theability to receive and unpack zip files. A discard icon 524 allows theuser to delete the current file 508 and any accompanying data.

Filter 516 can be used to identify the beginning and end times of aseries of deflection signals along a ride. For example, processor 24 canselectively analyze filtered deflection signals for zenith positiondata, velocity data, acceleration data, force data, and work dataanalysis. Display 26 generates a visual representation of the filteredvelocity data versus zenith position data and/or velocity data versuswork data for those events selected in the time domain. Filter 516 canidentify specific event types (e.g., right-hand turns or jumps) toselect specific displacement data or acceleration data corresponding tothat event type. Using the filter 516 in this way generates a velocityversus force/work visual representation for the identified event typesbased on the filtered data.

Filter 516 may be used between any two pins. Pins can be droppedthroughout a ride. A pin is simply a GPS location at a particular time.If GPS is not present, the pin is a marker at a particular point of therecording. To filter, tap the filter 516 icon, select start and end pin.The analysis excludes unfiltered events and analyzes the filtered eventsthat were recorded between the start pin and the end pin.

The basic statistics 526 of a ride can be recorded on the summaryresults page 500. The basic statistics 526 may include the start timeand date of a ride, the elapsed time of the ride and the time thesensors were streaming. The GPS moving time may measure the time thatthe bike was moving and the ride segments may show any breaks in thedata stream (e.g., for breaks where the bike is not moving). System 10displays similar basic statistics 526 for the shock 14 in the rear shockcomponent 504.

The front axle statistical results are unique to the front axle, but therear axle also has similar rear axle statistical metrics. The statisticscan be divided into displacement statistics 528, compression statistics530, and rebound statistics 532. For example, the percentage of filteredsampled and analyzed, the minimum, maximum, and average axle positions,and the total axle movement may be recorded as the displacementstatistics 528. The compression count, maximum and average compressionrate, and statistical two sigma compression rate may be included as thecompression statistics 530. Similar measurements for the rebound count,max and average rebound rate, and two sigma rebound rate may be includedin the rebound rate 532.

Based on the displacement and front axle statistics, dynamic forces suchas vibration statistics can be determined. Vibration measurements 534may include relative compression, rebound, and/or other statistics. Thefork movement/or vibration ratios 536 may have absolute compression,rebound, and/or other statistics. The summary results page 500 for therear suspension component 504 may include similar statistics.

FIG. 9 is a continuation of FIG. 8 (e.g., when a user scrolls down onthe basic statistics 526 module of the results module 126). For example,vibration measurements 534 and vibration ratios 536 are displayed. Thevibration analysis 533 includes vibration averages showing the values inmultiples of gravity (e.g., a 6.33 g compression average) and a strokeanalysis 540 of the compression and rebound events. System 10 visualizesthe data as a speed (m/s) versus elevation (m) plot 542. The elevation544 (measured in meters) decreases as the rider comes down a mountainand the speed 546 gradually increases.

FIG. 10 displays the cumulative number of compressions and reboundspeeds for a given ride as a histogram. For example, the histogramindicates a compression speed 602 at approximately 576 mm/s resulted in185 compressions for this ride. Similarly, only 3 compressions exceededa 3,456 mm/s compression speed. System 10 generates a similar histogramfor the rebound speed 604 indicating the rebound speeds in mm/s for allthe rebound events. For example, FIG. 10 illustrates 93 rebounds with anapproximate speed of 750 mm/s.

FIG. 11 illustrates a recorded waveform 700 in the time domain. Therecorded waveform 700 has several filters including theposition/displacement filter 702, the speed filter, 704, the fork filter706, and the shock filter 708. Several filters may be selectedsimultaneously for different visualizations of the raw data. Forexample, FIG. 9 illustrates a displacement plot 710, a speed plot 712and an acceleration plot of the shock filter 708. Similar data can beobtained for the fork filter 706. In some embodiments, the fork filter706 and the shock filter 708 may be plotted simultaneously.

FIG. 12 illustrates a zoomed in (e.g., a 10 second framed view)perspective of the displacement plot 710 and the speed plot 712illustrated in FIG. 11. The waveforms in FIG. 12 show the continuity ofthe displacement plot 710 and speed plot 712. Only when the time domainis large does the representation create the sharp vertical linesrepresenting extreme events shown in FIG. 11.

The results module 500 of FIG. 8 includes a balance component 506introduced above. The balance component 506 relates fork 12 data toshock 14 data to determine overall suspension system 11 performance.When the user touches the balance component 506 in FIG. 8, system 10opens a balance results module 800 shown in FIG. 13.

As illustrated in FIG. 13, the balance data includes a toggle filter toselect zenith data 802 acquired at the reversal of a compression orrebound, maximum data 804 that includes only the maximum values for anevent and excludes other data, and travel data 806. Travel data 806includes all collected data. The user can filter data based on the forkfilter 810, shock filter 812, or both (e.g., filter 814). Asillustrated, the suspension system 11 balance 506 of zenith data 802 forboth the fork 12 and shock 14 is selected. This creates scatter-plots ofzenith data 802 for both the fork 12 (light dots and light line) and theshock 14 (dark dots/line). The compression scatter-plot 815 includesdata points for the speed of compression versus the displacement causedin the damper. The maximum compression speed 816 is calculated as asigma regression line (e.g., a 6 sigma extreme theoretical valueindicating the maximum compression speed). Similarly, the minimum orlow-speed events are calculated as a sigma regression line for the data(e.g., a 6 sigma extreme theoretical value indicating minimumcompression speed). The light line or fork regression line 820 and thedark line or shock regression line 822 are created by the regressionanalysis of fork data 824 (indicated by a light dot) and shock data 826(indicated by a dark dot).

The regression analysis of the fork regression line 820 and shockregression line 822 provides an way to determine the balance ofsuspension system 11. Applicant has found that when the fork regressionline 820 and shock regression line 822 are parallel, or nearly parallel,the suspension system 11 is balanced. For example, the illustratedsuspension system 11 is more balanced in the compression scatter-plot815 than in the rebound scatter-plot 830. This gives the rider a quickway to visualize the data and adjust the settings on the suspensionsystem 11.

The rebound scatter-plot 830 has similar features to the compressionscatter-plot and is used to visualize the balance on the suspensionsystem 11. For example, a minimum work 832 (or maximum rebound) andmaximum work 834 (or minimum rebound) are determined based on thetheoretical sigma values of statistical analysis. Similarly, the forkregression line 836 is based on the fork data 838. The shock regressionline 840 is determined based on the shock data 842. Thus, the regressionanalysis shown in the compression scatter-plot 815 and reboundscatter-plot 830 provide a method of visualizing the suspension systemsbalance for the combined spring rates of the fork 12 and shock 14working as a system.

As described above, the rider can select a GPS hyperlink 122, 514 on thehome-screen 100 or results page 500. GPS hyperlinks 122 and 514 maydisplay the GPS module 900 shown in FIG. 14. The GPS module 900 storesthe beginning or start 902 and end or finish 904 of a ride. This enablesthe operator to compare the analytical results obtained from a ride withthe difficulty and location of the ride. Competitors may tune a bike fora particular course, for example, by riding the course and visuallycomparing the data, as described. GPS module 900 may also remind theoperator to note the difficulty or strenuousness of a ride and makeadjustments accordingly. GPS module 900 can be linked to work with anyof the modules described above and supports the data obtained fromcontrol system 10.

The processor 24 described herein can be coordinated by operating systemsoftware, such as iOS, Android, Chrome OS, Windows XP, Windows Vista,Windows 7, Windows 8, Windows Server, Windows CE, Unix, Linux, SunOS,Solaris, iOS, Blackberry OS, VxWorks, or other compatible operatingsystems. In other embodiments, a proprietary operating system maycontrol the computing device. Conventional operating systems control andschedule computer processes for execution, perform memory management,provide file system, networking, I/O services, and provide a userinterface functionality, such as a graphical user interface (“GUI”),among other things.

The processors 24 described herein may implement the techniquesdescribed herein using customized hard-wired logic, one or moreApplication Specific Integrated Circuits (ASIC) or Field ProgrammableGate Arrays (FPGA), firmware and/or program logic which causesprocessors to be a special-purpose machine. According to one embodiment,parts of the techniques disclosed herein are performed by processor 24of FIG. 1 in response to executing one or more sequences instructionscontained in electronic memory. Such instructions may be read into orfrom memory from another storage medium, such as storage device.Execution of the sequences of instructions contained in memory causesthe processor 24 to perform the process steps described herein. Inalternative embodiments, hard-wired circuitry may be used in place of orin combination with software instructions.

Moreover, the various illustrative logical blocks and modules describedin connection with the embodiments disclosed herein can be implementedor performed by a machine. Examples include a processor device, aDigital Signal Processor (DSP), an ASIC, an FPGA or another programmablelogic device, discrete gate or transistor logic, discrete hardwarecomponents, or any combination thereof designed to perform the functionsdescribed herein. A processor device can be a processor 24, but in thealternative, the processor device can be a controller, microcontroller,or state machine, combinations of the same, or the like. A processordevice can include electrical circuitry configured to processcomputer-executable instructions. In another embodiment, a processordevice includes an FPGA or another programmable device that performslogic operations without processing computer-executable instructions. Aprocessor device can also be implemented as a combination of computingdevices, e.g., a combination of a DSP and a processor 24, a plurality ofprocessors 24, one or more processors 24 in conjunction with a DSP core,or any other such configuration. Although described herein primarilyconcerning digital technology, a processor 24 device may also includeprimarily analog components. For example, some or all of the renderingtechniques described herein may be implemented in analog circuitry ormixed analog and digital circuitry.

The processor 24 can store the processed images in memory and/ortransmit the images to a display 26. The processor 24 can transmit theimages to display 26 in real time. Display 26 includes any deviceconfigured to receive images and display or store the images. In someembodiments, display 26 is located at or near system 10. In someembodiments, display 26 is remote from system 10. In addition, display26 can include a device (e.g., memory) that stores data and/or signalsfor future analysis and verification. Such a display 26 effectivelydocuments and stores the data and/or signals.

Display 26 includes any device that receives a processed signal. Forexample, display 26 includes, but is not limited to, a mobile phone(e.g., a smartphone), monitoring devices, electronics systems, webcams,a television, a computer monitor, a computer, a hand-held computer, atablet computer, a laptop computer, a personal digital assistant (PDA),a digital video recorder (DVR), a multi-functional peripheral device,etc. Display 26 apparatuses can include unfinished products, lenses,and/or memory.

In system 10, electronic memory includes any non-transitorycomputer-readable storage medium. Memory can be located anywhere withinsystem 10. For example, system 10 can locate memory in display 26, aseparate computing device, the cloud, and/or in other locations.Processor 24 may access memory to obtain measured displacement and/oracceleration data. For example, the raw data, as well as the calculatedzenith position, velocity, force, work, and approximation curves (e.g.,regression lines), can be stored in memory. These program instructionscan reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROMmemory, registers, hard disk, a removable disk, a CD-ROM, or any otherform of a non-transitory computer-readable storage medium. Suchspecial-purpose computing devices may also combine custom hard-wiredlogic, ASICs, or FPGAs with custom programming to accomplish thetechniques described herein. The special-purpose computing devices mayinclude desktop computer systems, server computer systems, portablecomputer systems, handheld devices, networking devices or any otherdevice or combination of devices that incorporate hard-wired and/orprogram logic to implement the techniques.

It should be understood that the figures illustrate the exemplaryembodiments in detail, and it should be understood that the presentsystem 10 is not limited to the details or methodology set forth in thedescription or illustrated in the figures. It should also be understoodthat the terminology is for the purpose of description only and shouldnot be regarded as limiting.

Further modifications and alternative embodiments of various aspects ofthe invention will be apparent to those skilled in the art in view ofthis description. Accordingly, this description is to be construed asillustrative only. The construction and arrangements, shown in thevarious exemplary embodiments, are illustrative only. Although only afew embodiments have been described in detail in this disclosure, manymodifications are possible (e.g., variations in sizes, dimensions,structures, shapes and proportions of the various elements, values ofparameters, mounting arrangements, use of materials, colors,orientations, etc.) without materially departing from the novelteachings and advantages of the subject matter described herein. Someelements shown as integrally formed may be constructed of multiple partsor elements, the position of elements may be reversed or otherwisevaried, and the nature or number of discrete elements or positions maybe altered or varied. The order or sequence of any process, logicalalgorithm, or method steps may be varied or re-sequenced according toalternative embodiments. Other substitutions, modifications, changes,and omissions may also be made in the design, operating conditions andarrangement of the various exemplary embodiments without departing fromthe scope of the present invention.

What is claimed is:
 1. A system for adjusting a damping force on thesuspension of a bicycle, comprising: a front shock sensor coupled to afront shock of a bicycle to generate a vertical front shock deflectionsignal representative of the vertical deflection of the front shock; arear shock sensor coupled to a rear shock of a bicycle to generate avertical rear deflection signal representative of the verticaldeflection of the rear shock; a processor coupled to the sensors, togenerate front shock velocity data representative of a verticalcomponent of velocity of the front shock based upon the signals,generate rear shock velocity data representative of a vertical componentof velocity of the rear shock based upon the signals, generate zenithposition data for the front shock representative of a verticaldisplacement based on the front shock deflection signal, and generate anapproximation curve video signal based upon the velocity data and zenithposition data; and generate zenith position data for the rear shockrepresentative of a vertical displacement based on the rear shockdeflection signal, and generate an approximation curve video signalbased upon the velocity and zenith position data; and a display coupledto the processor configured to simultaneously generate a visualrepresentation of the velocity to zenith position data based upon theapproximation curve video signal computed for the front shock and therear shock, the visual representation comprising a curve fit analysis ofthe velocity data versus zenith position data for the front shock andthe rear shock, wherein adjustments to the damping force of the frontshock and rear shock are based upon the curve fit analysis.
 2. Thesystem of claim 1, wherein the processor filters data points of thevertical components of front shock and rear shock displacement data forevents upon which the analysis is based, wherein the display outputsvisual representations of the filtered data points for the front shockand rear shock as a curve fit of a rebound and damping velocity versuszenith position for each event.
 3. The system of claim 1, wherein thedisplay is an application on a smartphone or a tablet.
 4. The system ofclaim 1, wherein recorded waveforms of the vertical displacement signalsgenerate zenith position, velocity, acceleration, force, and work datafor the front shock and rear shock, wherein the recorded waveforms arepresented in a time domain.
 5. The system of claim 1, wherein theprocessor computes the velocity and zenith position data for recordedevents and generates front shock and rear shock regression lines of thevelocity data versus zenith position data, wherein a slope of the frontshock regression line is compared to a slope of the rear shockregression line to establish the recommended adjustments of the frontshock and the rear shock, the recommended adjustments setting the frontshock and rear shock regression line slopes within 15° of parallel. 6.The system of claim 1, wherein the processor computes total work fordeflection and rebound of the front shock and rear shock, the total workbeing a function of the deflection data and force data, wherein theprocessor generates front shock regression lines and rear shockregression lines of the total work versus velocity data and force dataversus velocity data and calculates recommended adjustments of the frontshock and the rear shock that sets a slope of the front shock regressionlines and a slope of the rear shock regression lines within 15° ofparallel.
 7. The system of claim 1, further comprising a GPS recorderthat correlates the deflection signals for the front shock and rearshock into events corresponding to a tracked GPS location.
 8. The systemof claim 1, further comprising electronic storage to store the generateddata, wherein the processor generates zenith position data and velocitydata from displacement signals collected from a plurality of ridesstored in electronic storage.
 9. The system of claim 1, furthercomprising a filter to identify a beginning time and end time of aseries of deflection signals along a ride, the processor analyzing thefiltered deflection signals for zenith position data, velocity data,acceleration data, force data, and work data analysis, and the displaygenerating a visual representation of the velocity data versus zenithposition data and velocity data versus work data.
 10. The system ofclaim 1, further comprising a filter to identify event types that selectdisplacement data for generating a velocity versus zenith positionvisual representation for the identified event types based on theselected displacement data.
 11. A system for adjusting a damping forceon a suspension of a bicycle, comprising: a front shock sensor coupledto a front shock of a bicycle to generate a vertical fork accelerationsignal representative of the vertical acceleration of the front shock; arear shock sensor coupled to a rear shock of a bicycle to generate avertical rear acceleration signal representative of the verticalacceleration of the rear shock; a processor coupled to the sensors, togenerate front shock velocity data representative of a verticalcomponent of velocity of the front shock based upon the signals,generate rear shock velocity data representative of a vertical componentof velocity of the rear shock based upon the signals, generate zenithposition data for the front shock representative of a zenith positionbased on the acceleration signal of the front shock, and generating anapproximation curve video signal based upon the velocity and zenithposition data; and generate zenith position data for the rear shockrepresentative of a zenith position based on the acceleration signal ofthe rear shock, and generating an approximation curve video signal basedupon the velocity and zenith position data; and a display coupled to theprocessor configured to simultaneously generate a visual representationof the velocity to zenith position based upon the approximation curvevideo signals computed for the front shock and rear shock, the visualrepresentation comprising a curve fit analysis of the vertical componentof velocity versus zenith position of the front shock and the rearshock, wherein the display recommends adjustments to the damping forceat the front shock and rear shock based upon the curve fit analysis. 12.The system of claim 11, wherein the processor generates verticaldisplacement data and calculates a vertical component of work as afunction of the force and displacement of recorded events, wherein thevertical component of work at the front shock and rear shock generaterecommended settings for the events at the front shock and rear shockbased on a curve fit analysis of the vertical work components.
 13. Thesystem of claim 11, wherein the processor generates front shock and rearshock velocity data and zenith position data for two or more rides, andthe display obtains results from the processor to generate the visualrepresentation for the two or more rides.
 14. The system of claim 11,wherein the processor generates vertical velocity data versus elevationfor ride events, and the display outputs a graph of the verticalcomponent of velocity data versus elevation.
 15. The system of claim 11,wherein the processor generates histograms for events with an equalcompression velocity and an equal rebound velocity, and the displaygenerates a visual representation of a number of events with equalcompression velocities and the number of events with equal reboundvelocities.
 16. The system of claim 11, wherein the display is output inreal-time, the processor generating velocity data and zenith positiondata during an event and the display generates a visual representationof the velocity to zenith position based upon the approximation videosignal computed for the front shock and rear shock in real-time duringthe event.
 17. The system of claim 11, wherein the display is output toan application on a smartphone or tablet.
 18. The system of claim 11,further comprising a record module that records data at a fixedfrequency and couples to the display to generate waveforms of thevertical component of the displacement, velocity, and acceleration ofthe front shock and rear shock in a time domain.
 19. The system of claim11, further comprising a filter that filters events according touser-defined inputs, the velocity data and zenith position data for thefront shock and rear shock only including the events filtered accordingto the user-defined inputs, wherein the display generates a visualrepresentation of the velocity to zenith position based on the filteredevents.
 20. A device for displaying parameters of a suspension systemfor a bicycle, the device comprising, electronic memory to store userinputs and result data for a front shock and a rear shock; a setupmodule to obtain information related to the front shock and the rearshock on a suspension system of the bicycle, the setup modulecomprising: a front shock module to obtain a calibrated verticaldisplacement of the front shock; and a rear shock module to obtain acalibrated vertical displacement of the rear shock; a record module thatrecords events during a ride, the record module obtaining the zenithposition, vertical displacement, velocity, and acceleration of the frontshock and rear shock for each event and storing the zenith position,vertical displacement, velocity, and acceleration of the front shock andthe rear shock in electronic memory; a results module that accesses theresults of the record module and setup module to calculate verticalzenith position versus vertical velocity components for each event atthe front shock and rear shock, the results module generating a curvefit analysis of the vertical zenith position component versus velocityfor the front shock and rear shock and generating a curve fit analysisof the vertical velocity component versus zenith position of the frontshock and rear shock, the results module comparing the curve fitanalysis for the zenith position and velocity components at the frontshock with the curve fit analysis for the zenith position and velocitycomponents at the rear shock; and a display to output recommended dampersettings for the front shock and the rear shock based on the comparisonof the curve fit analysis for zenith position and velocity components ofthe front shock and the rear shock.